Skip to content

Conversation

@jodavies
Copy link
Collaborator

@jodavies jodavies commented Nov 28, 2024

Reset of *AR.CompressPointer was the wrong side of an #ifdef WITHZLIB.

Also fix the --without-zlib build, broken since the split sort allocation patch: 7d0e71d

Partially closes #95 ?

Reset of *AR.CompressPointer was the wrong side of an #ifdef WITHZLIB.

Also fix the --without-zlib build, broken since the split sort allocation
patch: 7d0e71d
@coveralls
Copy link

coveralls commented Nov 28, 2024

Coverage Status

coverage: 50.587% (+0.2%) from 50.437%
when pulling 46b1fbf on jodavies:fix-issue-95b
into 3de97ac on vermaseren:master.

Copy link
Collaborator

@tueda tueda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have confirmed that this PR fixes #95 (comment) (or
#95 (comment)) without zlib. (The source code remains unchanged with zlib.)

Is the suffix b in the test case name Issue95b intended to suggest a partial fix?

@tueda tueda added this to the v4.3.2 milestone Dec 1, 2024
@jodavies
Copy link
Collaborator Author

jodavies commented Dec 1, 2024

Yes exactly, this issue is not really anything too do with the original gzip issue of #95 (fixed in 26793e4), we just found it there while testing.

A test case was never added for the original gzip but, I will add one as part of this PR. I just need to check how long the test case I found takes to run under valgrind, maybe it needs further trimming down to be suitable.

Regarding the further reports of the gzip bug, I never managed to reproduce any of them. Looking back at the discussion, no one actually confirmed that they were using a post - 26793e4 binary. It is possible, that #95 can now be closed...

@jodavies
Copy link
Collaborator Author

jodavies commented Dec 2, 2024

Thanks. Fixed those.

@jodavies
Copy link
Collaborator Author

jodavies commented Dec 2, 2024

Looking back at the discussion, no one actually confirmed that they were using a post - 26793e4 binary.

This is not true actually, @alonli1 's log files are FORM 5 beta.

Also of note, is that those two subsequent reports are zerror -3 and not -2 like the original report. This issue should remain open I suppose...

This was fixed a long time ago, but no test case was added. Add one
now, just in case. This fails pre 26793e4 for form and tform -w2,
but not tform -w4. Skip it for valgrind tform, since it takes a long
time to run.
@tueda
Copy link
Collaborator

tueda commented Dec 2, 2024

I feel the discussions in #95 have become rather lengthy. Maybe we could extract and summarize the remaining problems and create a new issue for them, then this PR could close it.

Copy link
Collaborator

@tueda tueda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix. Now it looks good.

@jodavies
Copy link
Collaborator Author

jodavies commented Dec 2, 2024

Yes, that works for me. I think it is also not impossible that zerror=-3 there can come from bad hardware, since the issue seems not to be reproducible, and also @jamievicary 's crash was form and not tform, so is a bit more deterministic.

@jodavies jodavies merged commit 3262c64 into form-dev:master Dec 2, 2024
70 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

gzip errors

3 participants